Authorization access controlled content exchange

ABSTRACT

Authorization access controlled content exchange can be implemented, for example, in a multimedia content distribution environment when individual client devices are capable of storing content. A content index is maintained for each client device that reflects the content stored thereat. Predefined authorization access information for each relevant content item may be included in a content index entry corresponding thereto. A profile is maintained that includes predetermined authorization access information which indicates access rights. A search may be performed by and/or on behalf of a requesting client device for desired content with reference to authorization access information. A content transfer to the requesting client device from a target client device may be enabled if the predetermined authorization access information comports with the predefined authorization access information. Searches may be orchestrated or effectuated by the requesting client device or a head end of the multimedia content distribution system.

TECHNICAL FIELD

This disclosure relates in general to controlled content exchange and inparticular, by way of example but not limitation, to content sharingacross client devices that is controlled responsive to authorizationaccess information.

BACKGROUND

Television-based entertainment systems are expanding the programming andservices that they offer. In addition to television program content suchas that found on broadcast and traditional cable networks, televisionservice providers are adding on-demand video, as well as otherinteractive services, features, and applications. The correspondingcontent and additional information are downloaded over atelevision-based network for display, use, and/or storage on client-sideset-top boxes (STBs) or similar devices. Enabling content storage isprovided as a service and/or feature to subscribers in television-basedentertainment systems.

The storage is typically accomplished using a hard disk or other massmemory storage medium in which the audio/video or other content is savedusing any of many available formats, including those formats thatcompress the content. A subscriber can therefore order the STB to recordcontent onto the hard disk by setting a channel, date, and time or byselecting a program listed on an electronic program guide (EPG).Subsequently, the subscriber can view the recorded content at his or herleisure. However, the subscriber is not always able to record programsthat he or she may wish to subsequently view.

There may be many reasons for a subscriber failing to record a desiredprogram. For example, there may be insufficient storage available on thehard disk. The subscriber may simply forget to order the STB to record adesired program, or the subscriber may be unaware that a desired programis to be broadcast prior to the broadcast. Alternatively, the EPG orother source of programming data may be inaccurate. Additionally, evenif the programming data is accurate, the subscriber is aware of theprogram, and the subscriber correctly sets the STB, the subscriber isnonetheless subject to last minute and/or unannounced scheduling changesas to time, day, or channel by the broadcasting network.

Accordingly, for television-based entertainment systems, there is a needfor schemes and techniques to provide a service and/or feature tosubscribers to handle situations in which subscribers fail to record adesired program.

SUMMARY

Authorization access controlled content exchange can be implemented, forexample, in a multimedia content distribution environment whenindividual client devices are capable of storing content. A contentindex is maintained for each client device that reflects the contentstored thereat. Predefined authorization access information for eachrelevant content item may be included in a content index entrycorresponding thereto. A profile is maintained that includespredetermined authorization access information which indicates accessrights. A search may be performed by and/or on behalf of a requestingclient device for desired content with reference to authorization accessinformation. A content transfer to the requesting client device from atarget client device may be enabled if the predetermined authorizationaccess information comports with the predefined authorization accessinformation. Searches may be orchestrated or effectuated by therequesting client device or a head end of the multimedia contentdistribution system. Content indexes of the client devices may besearched at the head end or at the individual client devices, dependingon implementation.

BRIEF DESCRIPTION OF THE DRAWINGS

The same numbers are used throughout the drawings to reference likeand/or corresponding aspects, features, and components.

FIG. 1 illustrates an exemplary television system architecture in whichthe systems and methods for authorization access controlled contentexchange can be implemented.

FIG. 2 illustrates an exemplary client device, a television, and variousinput devices that interact with the client device.

FIG. 3 is a block diagram that illustrates components of the exemplaryclient devices shown in FIGS. 1 and 2.

FIG. 4 is a network environment in which exemplary aspects ofauthorization access controlled content exchange are illustrated.

FIG. 5 is a flow diagram that illustrates an exemplary method forauthorization access controlled content exchange.

FIG. 6 is an exemplary head end of the network environment of FIG. 4.

FIG. 7 is an exemplary client device for the network environment of FIG.4.

FIG. 8 is an exemplary profile for the network environment of FIG. 4.

FIG. 9 is an exemplary content index for the network environment of FIG.4.

FIG. 10 illustrates an exemplary authorization access controlled contenttransfer for the network environment of FIG. 4.

FIGS. 11, 11A, and 11B are flow diagrams that illustrate exemplarymethods for authorization access controlled content exchange.

DETAILED DESCRIPTION

The following discussion is directed to an exemplary multimedia contentdistribution system such as a television-based entertainment system.Such systems include interactive TV networks, cable/satellite networksthat utilize electronic program guides and other applications,web-enabled TV networks, and so forth. Client devices in such systemsrange from full-resource clients with substantial memory and processingresources, such as TV-enabled personal computers and TV recordersequipped with hard-disks, to low-resource clients with limited memoryand/or processing resources, such as traditional STBs. However,authorization access controlled content exchange as described herein mayadditionally be used in other environments such as those that distributecontent with limitations regarding playability, recording, furtherdistribution, and so forth. While aspects of the described systems andmethods can be used in any of these environments and for any types ofclient devices, they are described primarily in the context of thefollowing exemplary environment.

Exemplary System Architecture

FIG. 1 illustrates an exemplary television-based entertainment system100 that is an architecture in which authorization access controlledcontent exchange may be implemented. System 100 facilitates distributionof content and other information to multiple viewers. System 100includes one or more content providers 102, zero, one or more otherinformation providers 104, a content distribution system 106, and one ormore client devices 108(1), 108(2), . . . , 108(N) coupled to contentdistribution system 106 via a network 110.

Content provider 102 includes a content server 112 and stored content114, such as movies, television programs, commercials, music, andsimilar audio and/or video content. Content server 112 controlsdistribution of stored content 114 from content provider 102 to contentdistribution system 106. Additionally, content server 112 may controldistribution of live content (e.g., content that was not previouslystored, such as live feeds) and/or content stored at other locations tocontent distribution system 106.

Other information provider 104 includes other information database 116and other information server 118. Other information database 116 storesother content information that may be provided to client devices 108.Such other content information includes software modules, images, text,executable programs, gaming or other interactive information, and soforth. Thus, the other information may also include multimedia content,especially content of an irregular, one-of-a-kind, or similar nature,content of an interactive type, or content from smaller independentproviders. Other information server 118 processes the other informationfrom other information database 116 prior to distribution to generateone or more files that are optimized for, or at least capable of,transmission to content distribution system 106 and/or distributiontherefrom.

Content distribution system 106 includes a transceiver 128, one or morecontent processors 130, and one or more other information processors132. Transceiver 128 can alternatively be a broadcast transmitter ifbidirectional communication is not required. Transceiver 128 transmits(e.g., broadcasts) signals, such as cable/satellite television signals,across network 110. Network 110 can include a cable television network;an RF, microwave, satellite, and/or data network, such as the Internet;and may also include wired or wireless media using any transmissionformat or protocol. Additionally, network 110 can be any type of network(including a broadcast network), using any type of network topology andany network communication protocol, and can be represented or otherwiseimplemented as a combination of two or more networks.

Content processor 130 processes the content received from contentprovider 102 prior to transmitting the content across network 110.Similarly, other information processor 132 processes the otherinformation that is received from other information provider 104 priorto transmission of the other information across network 110. Aparticular content processor 130 may encode, or otherwise process, thereceived content into a format that is understood by the multiple clientdevices 108(1), 108(2), . . . , 108(N) that are coupled to network 110.Content processor 130 and/or other information processor 132 may alsotag content with authorization access information prior to distributionto the client devices 108.

Although FIG. 1 shows a single content provider 102, a single otherinformation provider 104, and a single content distribution system 106,the exemplary system 100 can include any number of content providersand/or other information providers coupled to any number of contentdistribution systems. Thus, at least content distribution system 106,content provider 102, and/or other information provider 104 areindividually or jointly representative of a headend service thatprovides content and other information to multiple subscribers.

Client devices 108 can be implemented in a number of ways. For example,a client device 108(1) receives content and other information from asatellite-based transmitter via a satellite dish 134. Client device108(1) is also referred to as a set-top box or a satellite receivingdevice. Client device 108(1) is coupled to a television 136(1) forpresenting the content and other information (including audio, video,and/or audio/video content information) that are received by clientdevice 108(1), as well as for presenting a graphical user interface. Aparticular client device 108 can be coupled to any number of televisions136 and/or similar devices that can be implemented to display orotherwise render content. Similarly, any number of client devices 108can be coupled to a single television 136.

Client device 108(2) is also coupled to receive content and otherinformation from network 110 and to provide the received content andother information to associated television 136(2). Client device 108(N)is an example of a combination television 138 and integrated set-top box(STB) 140. In this example, the various components and functionality ofthe STB are incorporated into the television, rather than using twoseparate devices. STB 140 that is integrated into television 138 canreceive signals (e.g., broadcast signals) via a satellite dish (similarto satellite dish 134) and/or directly via network 110. In alternateimplementations, client devices 108 may receive signals via the Internetor any other network, especially those network mediums that are capableof handling so-called broadband transmissions. As is further describedbelow, client devices 108 may engage in content exchanges between anamong other client devices 108 under an authorization access informationcontrolled mechanism.

The exemplary system 100 also includes content information from othernetworks/network providers 142, which may provide content informationsuch as information streamed over the Internet, information receiveddirectly from a provider of the information, and so forth. Contentinformation from other networks/network providers 142 may be accessibleover network 110 (i.e., a network that also provides content informationand other information via content distribution system 106).Alternatively, content information from other networks/network providers142 may be accessible over a different network, including a wide areanetwork (WAN), the Internet, a public or private telecommunicationsnetwork, and so forth.

Exemplary Client Device

FIG. 2 illustrates an exemplary implementation 200 of a client device108 that is shown as a standalone unit that connects to a television 136and communicates with various input devices 204, 206, and 208. Clientdevice 108 can be implemented in any number of embodiments, including asan STB, a satellite receiver, a TV recorder with a hard disk, a digitalvideo record (DVR) (and playback system), a game console, an informationappliance, a personal computer (PC), a personal digital assistant (PDA),a mobile telephone (MT), a tablet PC, a pocket or hand-sized PC, and soforth.

Client device 108 includes a wireless port 202, such as an infrared (IR)or Bluetooth wireless port, for receiving wireless communications from aremote control device 204, a handheld input device 206, or any otherwireless device, such as a wireless keyboard. Handheld input device 206can be a personal digital assistant (PDA), handheld computer, wirelessphone, or the like. Additionally, a wired keyboard 208 can be coupled tocommunicate with client device 108. In alternate embodiments, remotecontrol device 204, handheld device 206, and/or keyboard 208 may use anRF communication link or other mode of transmission to communicate withclient device 108.

Client device 108 receives one or more (e.g., broadcast) signals 210from one or more broadcast sources, such as from a satellite or a cableor a broadcast network, including a broadcast implementation of network110 (of FIG. 1). Client device 108 includes hardware and/or software forreceiving and decoding a broadcast signal 210, such as an NTSC, PAL,SECAM or other TV system video signal. Client device 108 also includeshardware and/or software for providing the user with a graphical userinterface (GUI) such as a menu-driven interface. With a GUI or otherinterface, for example, a user can access various network services,configure client device 108, and/or perform other functions, includingrequesting the recording or transfer of content in conjunction with acontent exchange mechanism.

Client device 108 can communicate with other devices via one or moreconnections including a conventional telephone line or link 212, an ISDNlink 214, a cable link 216, an Ethernet link 218, a DSL link 220, andthe like. Client device 108 may use any one or more of the variouscommunication links 212-220 at a particular instant to communicate withany number of other devices, including other client devices 108 and/or ahead end of multimedia content distribution system. For example, inaddition to receiving content information over any one of communicationlinks 212-220, client device 108 may provide (e.g., transmit)information such as content, a search request, an index of recordedcontent items, etc. over communication links 212-220 or any other typeof communication link. Such other types of communication links mayinclude those appropriate for a local area network (LAN), a Bluetooth®network, an IEEE 802.11b-compliant network, or other wired or wirelessnetwork type.

Client device 108 generates video signal(s) 222 and audio signal(s) 224,both of which are communicated to television 136. Video signals 222 andaudio signals 224 can be communicated from client device 108 totelevision 136 via an RF (radio frequency) link, S-video link, compositevideo link, component video link, co-axial cable link, or othercommunication link. Although not shown in FIG. 2, client device 108 mayinclude one or more lights or other indicators identifying the currentstatus of the device. Additionally, client device 108 may include one ormore control buttons, switches, or other selectable controls forcontrolling operation of the device.

FIG. 3 illustrates selected components of exemplary client device 108that shown in FIGS. 1 and 2. Client device 108 includes a first tuner300 and an optional second tuner 302. The tuners 300 and 302 arerepresentative of one or more in-band tuners that tune to variousfrequencies or channels to receive television signals, as well as atleast one out-of-bound (OOB) tuner that tunes to the broadcastchannel(s) over which data information is broadcast (e.g., carouseled orotherwise transmitted) to client device 108.

Client device 108 also includes one or more processors 304 which processvarious instructions to control the operation of client device 108 andto communicate with other electronic and computing devices. Clientdevice 108 can be implemented with one or more memory components,examples of which include a random access memory (RAM) 306, a disk drive308, another mass storage component 310, and a non-volatile memory 312(e.g., ROM, Flash, EPROM, EEPROM, etc.). The memory components (e.g.,RAM 306, disk drive 308, mass storage 310, and non-volatile memory 312)store various instructions, configuration information, and/or contentinformation for client device 108.

Alternative implementations of client device 108 can include a range ofprocessing and memory capabilities, and may include more or fewer typesof memory components than those illustrated in FIG. 3. For example,full-resource clients can be implemented with substantial memory andprocessing resources, including the disk drive 308 to store content forreplay by the viewer. Low-resource clients, however, may have limitedprocessing and memory capabilities, such as a limited amount of RAM 306,a small disk drive 308 (if any), and limited processing capabilities ofa processor 304.

An operating system 314 as well as other electronically-executableinstructions may be stored in non-volatile memory 312 (and/or othermemory component(s) 306, 308, and 310) and executed on processor 304 toprovide a runtime environment. A runtime environment facilitatesextensibility of client device 108 by allowing various interfaces to bedefined that, in turn, allow programs/modules to interact with clientdevice 108. These electronically-executable instructions include, forexample, DVR instructions 316 for recording (and playing back) contentand controlled content exchange instructions 318. Controlled contentexchange instructions 318 may enable client devices 108 to locate and/ortransfer content between and among other client devices 108 inaccordance with authorization access information. Controlled contentexchange instructions 318, which are described further herein, mayoptionally operate in conjunction with a head end of a multimediacontent distribution system.

Client device 108 also includes a decoder 320 to decode a broadcastvideo signal, such as an NTSC, PAL, SECAM or other TV system videosignal. Processor 304, along with tuner(s) 300 and 302 and/or decoder320, also enables client device 108 to reconstruct audio and video froman MPEG-2 stream or other digital packet signal, whether compressed oruncompressed. Client device 108 can also include other componentspertaining to a television-based entertainment system which are notillustrated in this example. For example, client device 108 can includea user interface application and/or user interface lights, buttons,controls, and the like to facilitate viewer interaction with the device.

Client device 108 further includes a wireless interface 322, a networkinterface 324, a serial and/or parallel interface 326, and a modem 328.Wireless interface 322 allows client device 108 to receive inputcommands and other information from a user-operated input device, suchas from a remote control device or from another IR, Bluetooth, orsimilar RF input device. Network interface 324 and serial and/orparallel interface 326 allows client device 108 to interact andcommunicate with other electronic and computing devices via variouscommunication links, including communication links to other clientdevices 108. Modem 328 facilitates communication by client device 108with other electronic and computing devices via a conventional telephoneline. Although not shown in FIG. 3, client device 108 may also includeother types of data communication interfaces to communicate with otherdevices.

Client device 108 also includes an audio output 330 and a video output332 that provide signals to a television or other device that processesand/or displays or otherwise renders the audio and video information.Although shown separately, some of the components of client device 108may be implemented together in an application specific integratedcircuit (ASIC) or other manner. For example, electronically-executableinstructions (318) and associated processing abilities for authorizationaccess controlled content exchange may be integrated together onto oneor more ASICs instead of using more-general memory (e.g., 306, 312,etc.) and/or processing (e.g., 304, etc.) resources of a client device(108).

Additionally, a system bus (not shown) typically connects the variouscomponents within client device 108. A system bus can be implemented asone or more of any of several types of bus structures, including amemory bus or memory controller, a peripheral bus, an acceleratedgraphics port, or a local bus using any of a variety of busarchitectures. By way of example, such architectures can include anIndustry Standard Architecture (ISA) bus, a Micro Channel Architecture(MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics StandardsAssociation (VESA) local bus, and a Peripheral Component Interconnects(PCI) bus also known as a Mezzanine bus.

Authorized Access Controlled Content Exchange

FIG. 4 is a network environment 400 in which exemplary aspects ofauthorization access controlled content exchange are illustrated. A headend 402 and multiple client devices 108 are in communication with eachother over network 110. Head end 402 provides content and otherservices/features to client devices 108 over network 110. Head end 402may therefore correspond at least to one or more of content distributionsystem 106, content provider 102, other information provider 104, and/orcontent information from other networks/network providers 142. Althoughonly two client devices 108X and 108Y are illustrated in networkenvironment 400, many more client devices 108 are typically connected tonetwork 110.

Each client device 108 includes a profile 410, a (content) index 412,and (stored) content 414. Hence, client device 108X includes a profile410X, an index 412X, and content 414X, and client device 108Y includes aprofile 410Y, an index 412Y, and content 414Y. Profile 410 providesinformation regarding a user/subscriber, the client device itself,features and premium services that are subscribed to, and so forth.Profile 410 is described further below with reference to FIG. 8. Index412 includes multiple entries that are each directed to one or morecontent items that are stored in content 414. Each index entry of index412 may include an identification of the stored content, descriptiveinformation, access rights information, and so forth. Each index may bestored as a listing of index entries or in any other format or manner.Index 412 is described further below with reference to FIG. 9.

Head end 402 includes profiles 404 and indexes 406. Generally, profiles404 may include profiles 410 of client devices 108 that are connected tohead end 402 over network 110. Similarly, indexes 406 may includeindexes 412 of client devices 108 that are connected to head end 402over network 110. Specifically, profiles 404 and indexes 406 can includeat least profiles 410 and indexes 412, respectively, of those clientdevices 108 that subscribe to an authorization access controlled contentexchange service with head end 402. When a client device 108 changes anentry of profile 410 or index 412, head end 402 is notified so thatprofiles 404 or indexes 406 may be changed accordingly to ensure thatconsistency is maintained. Similarly, when a head end 402 makes achange, the respective client device 108 is notified to maintainconsistency.

Profiles 404 and indexes 406 may be organized in any fashion. Exemplaryorganizations include a listing of profiles 410 and indexes 412,respectively; a standard or specialized database format; and so forth.Each respective profile 410 n/index 412 n pair (not explicitly shown)from a particular client device 108 n may be linked at head end 402 as aprofile/index pair 408 n, as indicated by linking arrows 408(1), . . . ,408(N). This linking may be established logically, by proximate memorystorage, and so forth.

It should be understood that the information in, for example, profile410X and index 412X may not be identical to the information in the entryor entries of profiles 404 and 406 that correspond to client device 108X(e.g., a profile/index pair 408(X)). For example, the profile portion ofprofile/index pair 408(X) may include a network address identifier forclient device 108X while profile 410X may or may not include the networkaddress identifier for client device 108X. Also, although index 412X mayinclude descriptions, ratings, reviews, etc. of a recorded content item,the corresponding index portion of profile/index pair 408(X) need notinclude such details. Additionally, in direct search implementations asdescribed herein, profiles 404 and indexes 406 need not be present athead end 402. Likewise, although it would increase bidirectionalcommunication between client devices 108 and head end 402, profiles 410and indexes 412 need not be present at client devices 108 in searchserver implementations.

FIG. 5 is a flow diagram 500 that illustrates an exemplary method forauthorization access controlled content exchange. The six (6) methodblocks 502-512 of flow diagram 500 may be effectuated in networkenvironment 400 (of FIG. 4). However, the method may alternatively beimplemented in a different network environment and/or with differenthardware. At block 502, a content search request is received. Thecontent search request may be received, for example, by a client device108 from a user/requester/viewer/subscriber. Alternatively, the contentsearch request may be received by head end 402 from auser/requester/subscriber/client device 108. Consequently, a user,requester, subscriber, etc. may be a person operating a client device108 or the actual client device 108. At block 504, a content match islocated via a search. The search for the requested content is carriedout by searching the indexes 412 or the indexes 406. Direct searches maybe accomplished by searching indexes 412 that are located at clientdevices 108. Search server searches may be accomplished by searchingindexes 406 that are located at head end 402. These two search mannersare described further below.

At block 506, it is determined whether the requester has access rightsto the requested content. This determination is made with reference tothe profile 410 and/or the profile portion of the profile/index pair 408of the client device 108 that is used to make the request as well as theindex entry of the located content in an index 412 and/or in the indexportion of profile/index pair 408 of the client device 108 that is asuccessful target of the search. In other words, it is generallydetermined whether there is agreement between authorization accessinformation of the profile information of the requester and theauthorization access information of the content.

The authorization access information from the profile information of therequester may be located in profile 410 at the requesting client device108 and/or in profiles 404 at the head end 402. The authorization accessinformation of the content may be located in content index 412 at thetarget client device 108 and/or in indexes 406 at the head end 402.Also, the authorization access information of the content may be locatedin a special database (not shown in FIG. 4) that is at or otherwiseaccessible to head end 402. Specifically, it is determined whetherpredetermined authorization access information from the profile of therequester comports with predefined authorization access information ofthe requested content.

By way of example but not limitation, it may be determined whether arequester subscribes to a premium content service that originallybroadcast or otherwise provided the requested content, which has nowbeen located as being stored on a target client device 108. If therequester does subscribe to the premium content service, then therequester has access rights to the requested content. Conversely, if therequester does not subscribe to the premium content service, then therequester does not have access rights to the requested content. Adetermination as to whether the requester subscribes to the premiumcontent service may be bifurcated into (i) whether the requestersubscribed to the premium content service at the time of broadcast ofthe requested content and/or (ii) whether the requester subscribes tothe premium content service when the content search request isreceived/initiated and/or when the requested content is transferred tothe requester.

If the requester is determined to not have access rights (at block 506),then the requester is not provided access to the content at block 508.If, on the other hand, the requester is determined to have access rights(at block 506), then the requester can be provided access to thecontent. For example, the search results may be reported to therequester at block 510. In other words, the successful location of amatch for the requested content can be reported to the requester. Atblock 512, access to the requested content can be provided to therequester. For example, the requester can be provided the opportunity totransfer the requested content from the target client device 108 to therequesting client device 108 for storage and/or rendering thereat.

FIG. 6 is an exemplary head end 402 of network environment 400 of FIG.4. Head end 402 includes a search server 602, a client configurationserver (CCS) part 604, and a content exchange database 606. CCS part 604includes instructions for communicating information between head end 402and multiple client devices 108. The information may include, inaddition to general setup and/or configuration information, profileinformation and index information for content exchange database 606.Search server 602 enables head end 402 to search content exchangedatabase 606 responsive to a requested content search that is receivedfrom a requesting client device 108. Search server 602 may beimplemented in any of multiple possible manners. For example, searchserver 602 may be a set of electronically-executable instructions forsearching content exchange database 606. Alternatively, search server602 may be a physically separate server that includes content exchangedatabase 606. Such a physically separate server may be part-of,co-located with, or otherwise accessible to head end 402. Otherimplementations may instead be used to realize search server 602.

Content exchange database 606 may include profiles 404 and indexes 406.Each profile entry in profiles 404 may be linked to an index entry inindexes 406 according to user/client device 108. Thus, a link orprofile/index pair 408X corresponds to client device 108X (of FIG. 4),and a link or profile/index pair 408Y corresponds to client device 108Y.The amount of information in any given profile entry of profiles 404 orany given index entry of indexes 406, and any linkages therebetween, mayvary, especially in dependence on what searching abilities andresponsibilities are to be allocated to search server 602. For example,if search server 602 is to conduct an entire requested search anddetermine whether appropriate access rights are held by a requesterwithout contemporaneously interrogating any client devices, thensignificant information for all entries of both profiles 404 and indexes406 should be included in content exchange database 606. Alternatively,if search server 602 receives predetermined authorization accessinformation from a profile 410 of a client device 108 (e.g., as part ofthe search request or responsive to interrogation after finding asuccessful match), then profiles 404 need not be present as part ofcontent exchange database 606. Other combinations and implementations ofcontent exchange database 606 are possible, more of which are describedherein for example with reference to FIGS. 10-11B.

FIG. 7 is an exemplary client device 108 for network environment 400 ofFIG. 4. Client device 108 includes a profile 410, a content index 412,and stored content 414, as described generally above with reference toFIG. 4. An exemplary profile 410 and an exemplary index 412 aredescribed further below with reference to FIGS. 8 and 9, respectively.Client device 108 also includes a user interface (UI) for searching 702,a client configuration agent (CCA) part 704, and a search agent 706. CCApart 704 includes instructions for communicating information betweenclient device 108 and head end 402. For example, CCA 704 may contact CCS604 to communicate information from client device 108 to head end 402,or vice versa. The information may include, in addition to general setupand/or configuration information, profile information from profile 410and index information from index 412 that is destined for contentexchange database 606 (of FIG. 6), or vice versa.

Search UI 702 provides a user interface for a user through client device108 (and possibly a separate display device such as television 136 (ofFIG. 1)). The UI can be GUI-based, menu-driven, operable by remotedevice such as a hand-held remote or keyboard, and so forth. Forexample, a general services screen may provide an option for the user toselect a service or feature which relates to searching content that isstored at other client devices 108. Selecting this option with a remote,keyboard, etc. results in a screen being displayed in which the user caninput search criteria such as content name, content broadcast time, andso forth. In fact, the enterable search criteria can be any informationthat is or may be stored in the content index entry of index 412 thatcorresponds to the desired content item to which the search is to bedirected. Exemplary information that is includable in index entries ofindex 412 is described further below with reference to FIG. 9.

Search agent 706 responds to instructions received from the user viasearch UI 702. Thus, search agent 706 causes a search to be performedfor the desired/requested content. The search is carried out on contentindexes associated with other client devices 108. Search agent 706 iscapable of causing searches of these content indexes in multiplemanners. These manners include direct searching of indexes 412 usingsearch agent 706, indirect searching of indexes 406 of content exchangedatabase 606 using search server 602, some combination thereof, and soforth. Search agent 706 and/or search server 602 are also capable ofensuring that the user is only permitted to access content to which theuser has rights.

Search agent 706 thus causes the search to be performed with referenceto authorization access information. Search server 602 or search agent706 compares predetermined authorization access information from theprofile 410 and/or the profile portion of the profile/index pair 408 ofthe requesting client device 108 to predefined authorization accessinformation associated with the requested content. The predefinedauthorization access information is stored with the index entry of thecontent that is determined to match the search request. The index entrymay be found in the content index 412 or the content indexes 406,depending on whether a direct search or an indirect search,respectively, was performed.

Search agent 706 and/or search server 602 denies access to the locatedcontent if the predetermined authorization access information does notcomport with the predefined authorization access information. On theother hand, search agent 706 and/or search server 602 provides access tothe located content if the predetermined authorization accessinformation does comport with the predefined authorization accessinformation. Access can be provided by permitting the user to transferor to schedule a transfer of the requested/located content from theother or target client device 108 to the originating or requestingclient device 108 of the user. An exemplary search and transfer processis described further below with reference to FIG. 10.

FIG. 8 is an exemplary profile 410 for the network environment 400 ofFIG. 194. Profile 410 includes one or more profile entries 802. Profile410 includes predetermined authorization access information that isassociated with a client device 108 and/or a user thereof. In otherwords, the predetermined authorization access information may beportable with respect to client device 108 such that anyone using clientdevice 108 has access rights in accordance with the predeterminedauthorization access information. Or, the predetermined authorizationaccess information may be portable with respect to the user such thatthe user can authorize (e.g., using an ID/password combination or otherauthentication technique) any client device 108 to have access rights inaccordance with the predetermined authorization access information.

Exemplary profile entry 802(1) is a user information entry that includesidentification/billing information 804 and general service planinformation 806. Identification/billing information 804 relates toidentification and billing information for a subscriber/user. Generalservice plan information 806 relates to one or more general serviceplans to which the subscriber/user subscribes. For example, a cable orsatellite provider may offer three levels of basic packages, such assilver, gold, and platinum and five optional add-on packages. Each ofthe packages has corresponding channels to which the subscriber gainsaccess rights when subscribing thereto. General service plan information806 thus lists which basic and/or add-on packages to which the user hassubscribed. This exemplary user information entry or another entry mayalso include information directed to parental rights that limitviewable/transferable content based on age-appropriateness ratings,including those separated into different types of material such aslanguage, violence, and so forth.

Exemplary profile entry 802(2) is a premium service entry that includessubscription date(s) information 808 and sub-authorization(s)information 810. Each premium service entry corresponds to a premiumservice provider, for example a service provider that providesmultimedia content for an additional, separate fee over and above thosecharged for general subscription packages. Subscription date(s)information 808 indicates whether the user is a subscriber to thecorresponding premium service provider. For example, astarting/enrolling subscription date may be included. Additionally, acurrent date, a current status, and/or a date of cessation/terminationof the premium service subscription may be included.Sub-authorization(s) information 810 relate to possible secondary orsecond-tier channels associated with a primary or first-tier premiumservice provider. Alternatively, a single premium service “entry” maylist all premium services to which a user subscribes instead of havingseparate “entries” for each premium service provider.

Exemplary profile entry 802(N) is a general access authorization entrythat includes code(s) information 812 and parameter(s) information 814.The general access authorization information of profile entry 802(N) mayinclude any information that indicates a user has rights to view,record, etc. content. In other words, the general access authorizationinformation of profile entry 802(N) can comprise data protectingbroadcast rights across recorded media. For example, such information ordata may pertain to content originating from intermittent providers suchas pay per view services. In a pay per view example, code(s) information812 may indicate or evidence rights to a particular content item.Parameter(s) information 814, if present, may indicate the number oftimes the particular content item may be viewed, recorded, transferred,etc. before any such rights expire.

FIG. 9 is an exemplary content index 412 for network environment 400 ofFIG. 4. Content index 412 includes one or more content entries 902. Eachcontent item stored in content 414 (of FIGS. 4 and 7) may include anassociated content entry 902. Each content entry 902 includesinformation that is related to the associated content and that may besearched, either directly or indirectly, by search agents 706 of otherclient devices 108. Content index entries 902 that are associated withcontent items that require special access rights have predefinedauthorization access information. The predefined authorization accessinformation indicates what access rights are needed to view, record,transfer, etc. the associated content item and/or the identity of therights holder.

Exemplary content entry 902(1) includes identification information 904.Identification information 904 identifies the associated content item.Exemplary content entry 902(2) includes identification information 904and rights holder information 906. Rights holder information 906includes the company, service provider, etc. that holds the viewing,recording, transferring, etc. rights to the associated content item.Each content entry 902 may include any combination of the informationtypes described for content entries 902(1), 902(2), and 902(N).

Exemplary content entry 902(N) includes name information 908, premiumservice identification 910, description, ratings, reviews, etc.information 912, and recording date and time information 914. Nameinformation 908 includes the name of the content item such as a title ofa program, movie, or event. Premium service identification information910 identifies the premium service provider of the content item by name,code, or the like. Description, ratings (including quality ratings andage-appropriateness ratings), reviews, etc. information 912 includes oneor more of a description, a summary, rating(s), review(s),actors/producers/and other artists of the content item, length of thecontent item, date of production/creation of the content item, and soforth. Recording date and time information 914 includes the date andtime at which the recorded content was broadcast and/or recorded. Thebroadcasting channel may also be recorded.

FIG. 10 illustrates an exemplary authorization access controlled contenttransfer for the network environment 400 of FIG. 4. The description ofFIG. 10 includes maintaining consistency between indexes in the contextof recording content. This context is indicated by numerals 1-3 that arewithin circles. The description of FIG. 10 also includes a contentsearch with reference to authorization access information in the contextof transferring content from one client device to another client device.This context is indicated by numerals 1-6 that are within rectangles.

It is assumed that users of client devices 108X and 108Y subscribe to acontrolled content exchange service. In this example, client device 108Xis searching for content that is located at client device 108Y. Theindication numerals in the circles and rectangles focus on thisassumption and this example. Furthermore, although content exchangedatabase 606 is illustrated with head end 402, it need not be present ifindirect searching via search server 602 is not to be implemented.

At {circle around (1)}, profile 410X and profile 404X are established toreflect the controlled content exchange service subscription. Also,index 412X and index 406X are maintained to be consistent with eachother. At {circle around (2)}, a user orders client device 108X torecord/save content to content 414X. An index entry is added to index412X for the stored content item to reflect that the content item is nowstored on client device 108X. At {circle around (3)}, this new entry iscommunicated to head end 402 and added to index 406X for user 408X.Communicating information between client device 108X and head end 402for the profiles and indexes, as well as for other information, may beaccomplished using CCA 704X and CCS 604.

At

, the user interacts with search UI 702X to request a content search.The search can be based on the name of the desired content or any otherinformation that is stored in the content entries of content indexes 406or 412. Examples of such information are described further above withreference to FIG. 9. At

, search agent 706X is launched to conduct the search (i.e., to causethe search to be performed). Search agent 706X may cause the search tobe performed indirectly using search server 602 of head end 402,directly by contacting other client devices 108 via network 10, and soforth.

For an indirect search implementation at

, search server 602 searches indexes 406 that correspond to multipleclient devices 108 of content exchange database 606 until a match isfound at index 406Y of user 408Y (corresponding to client device 108Y).For a direct search implementation at

, search agent 706X searches indexes 412 that correspond to multipleclient devices 108 that are connected to network 110 until a match isfound at index 412Y of client device 108Y (corresponding to a user 408Y(not explicitly shown)). Network addresses for potential target clientdevices 108, if not already present at client device 108X, may bedownloaded from head end 402 (e.g., from profiles 404). This directsearch can optionally rely on search agents 706 of potential targetclient devices 108 to effectuate the individual searches. For example,search agent 706X may send a search query to search agent 706Y andpermit/request search agent 706Y to search index 412Y of client device108Y.

At

, search server 602 or search agent 706X/706Y ascertains a match for therequested content. This match is communicated to search agent 706X alongwith any relevant information for transferring the desired content fromclient device 108Y to client device 108X. Such relevant information mayinclude a time when the desired content may be transferred and anestimated duration for the transfer process to be completed. At

, the user of client device 108X is given a chance to elect to have thedesired content transferred from client device 108Y to client device108X using search UI 702X. At

, search agent 706X communicates with search agent 706Y to establish atime and any relevant parameters for transferring the requested content.At

, the requested content is transferred from content 414Y of clientdevice 108Y to content 414X of client device 108X using, for example,search agent 706Y and search agent 706X. It should be understood thatany of the above communications or content transfers may alternativelybe effectuated using CCA 704X and CCS 604 or CCA 704Y.

Methods for Authorized Access Controlled Content Exchange

Authorized access controlled content exchange may be described in thegeneral context of electronically-executable instructions. Generally,electronically-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types.Authorized access controlled content exchange may also be practiced indistributed computing environments where functions are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment,electronically-executable instructions may be located in both a head endand in multiple remote client devices.

The methods and processes of FIGS. 5, 11, 11A, and 11B are illustratedin flow diagrams divided into multiple blocks. However, the order inwhich the methods and processes are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order to implement one or more methods or processes forauthorized access controlled content exchange. Furthermore, although themethods and processes are described below with reference to televisionentertainment environments 100 and 200, with reference to networkenvironment 400, and with reference to client devices 108 whereapplicable, the methods and processes can be implemented in any suitablenetwork environment and using any suitable hardware, software, firmware,or combination thereof.

FIGS. 11, 11A, and 11B are flow diagrams 1100, 1106A, and 1106B,respectively, that illustrate exemplary methods for authorization accesscontrolled content exchange. Flow diagram 1100 includes five (5) blocks1102, 1106, and 1110-1114. Method block 1106 represents two alternativeapproaches that each includes multiple other blocks. These twoalternative approaches are illustrated in FIGS. 1A and 1B as flowdiagrams 1106A and 1106B, respectively.

At block 1102 of flow diagram 1100, a search request for content isreceived from a user. For example, a search request can be received froma subscriber at a client device 108, or a search request can be receivedfrom a client device 108 at a head end 402. At block 1106, the searchrequest is processed. Two exemplary approaches for processing the searchrequest are illustrated at FIGS. 11A and 11B. The input and output flowsof the search request processing of block 1106 are indicated by flowarrows 1104 and 1108, respectively; these flow arrows 1104 and 1108 arereproduced in flow diagrams 1106A and 1106B for clarity. FIG 11Aillustrates an approach in which a search is performed if the requestinguser has any needed special rights. FIG. 11B illustrates an approach inwhich a search may be performed or started before knowing if therequesting user has any special rights that may be needed to access therequested content.

In flow diagram 1106A of FIG. 11A, it is determined whether any specialrights are needed to access the requested content at block 1116. Thisdetermination may be made at a client device 108 or a head end 402. Forexample, client device 108 may be able to “quickly” determine that therights holder of the requested content is a premium service providerbased on information from an EPG that evidences that the premium serviceprovider provided the requested program or based on a channel providedin the content request. Alternatively, head end 402 may make thisdetermination by consulting a special database that associates contentwith the rights holder or holders thereof.

If special rights are determined to be needed (at block 1116), then itis determined whether the user has such rights at block 1118. Thisdetermination may be accomplished by comparing the special rightsinformation (e.g., the predefined authorization access information)attained in block 1116 to predetermined authorization access informationof profile 410/404 of the requesting client device 108, for example athead end 402. At client device 108, on the other hand, thisdetermination may be accomplished by reviewing profile 410 and comparingthe information therein to any ascertained rights holder information.

If the user does not have the needed special rights (as determined atblock 1118), then it can be reported to the user that no search wasperformed and that no access to the content is currently available tothe user at block 1120. This reporting can be accomplished using asearch UI 702, for example. The multimedia content distribution systemmay also give the user an opportunity to subscribe to the premiumservice or otherwise pay a fee in order to gain access to the content atblock 1120.

If no special rights are needed (as determined at block 1116) or specialrights are needed to access the content but the user possesses suchrights (as determined at blocks 1116 and 1118), then the search isperformed at block 1122. The search may be performed indirectly using asearch server 602 and a content exchange database 606 of head end 402 ordirectly using a search agent 706 of the requesting client device 108and indexes 412 of target client devices 108. Alternatively, searchserver 602 can be enabled to search indexes 412 of target client devices108 to maintain greater control at head end 402, to decrease any privacyconcerns, and so forth.

If a match is not found at block 1124 from the search (of block 1122),then a no match search result is reported to the user at block 1126.This can be reported using a CCS 604 and CCA 704 for communicationsbetween client device 108 and head end 402 and/or using a search UI 702for communications between client device 108 and a viewer. If, on theother hand, a match is found at block 1124 from the search (of block1122), then the method can continue at block 1110 (of FIG. 11) asindicated by flow arrow 1108. Blocks 1110-1114 of flow diagram 1100 aredescribed further below.

In flow diagram 1106B of FIG. 11B, a search for the requested content isperformed at block 1128. The search may be performed indirectly using asearch server 602 and a content exchange database 606 of head end 402 ordirectly using a search agent 706 of the requesting client device 108and indexes 412 of target client devices 108. In either search manner,information input as parameter(s) for the search that is related to therequested content is compared to information in the indexes 406 or 412.If a match is not found at block 1130, then the absence of a match isreported to the user at block 1132. This report can occur between headend 402 and requesting client device 108 and/or between the clientdevice 108 and a viewer. If, on the other hand, a match is found atblock 1130, then the search results are adjusted responsive toauthorization access information.

This adjustment may be accomplished at least partly by comparingpredetermined authorization access information of a profile entrycorresponding to the requesting client device 108 to predefinedauthorization access information of an index entry corresponding to therequested content that was located (at blocks 1128 and 1130). For thepredetermined authorization access information to comport with thepredefined authorization access information in this particularimplementation, the user needs to have rights to the requested contentbased on the rights holder and based on the dates of those rights. Inother words, not only does the user need to have a subscription with therights holder, the user needs to have had the subscription at the timeof broadcasting of the requested content.

At block 1134, it is determined whether the user had rights to therequested content at the time of the broadcast. If the user did not haverights at the time of the broadcast, then it is reported to the userthat no access is available at block 1136. However, the user mayoptionally be given the option to subscribe and/or pay a fee in order togain access to the requested content. If, on the other hand, the userdid have rights at the time of the broadcast (as determinable in block1134), then it is determined or verified that the user currently hasrights to the requested content at block 1138. If the user does notcurrently have rights, then the no access report is provided to the user(at block 1136). If the user does have rights currently (as determinablein block 1138), then the method can continue at block 1110 (of FIG. 11)as indicated by flow arrow 1108.

Assuming that a content match is found during the search requestprocessing of block 1106, the match is reported to the user at block1110. The reporting can include an inquiry directed to whether the userwishes to accept the opportunity to transfer the located content. If thecontent transfer opportunity is accepted, the requesting client device108 can schedule a transfer time with the target client device 108 atblock 1112. After the transfer of the content, at block 1114 the indexat head end 402 that corresponds to requesting client device 108 isupdated to reflect the content that is now stored thereat. The contenttransfer itself may also be logged at the head end. Thus, in eithercase, the event is recorded at head end 402.

CONCLUSION

Although systems and methods have been described in language specific tostructural features and/or methods, it is to be understood that theinvention defined in the appended claims is not necessarily limited tothe specific features or methods described. Rather, the specificfeatures and methods are disclosed as exemplary forms of implementingthe claimed invention.

1. A method for authorization access controlled content exchange, the method comprising actions of: causing a plurality of content indexes to be searched to locate a match to requested content, each content index of the plurality of content indexes corresponding to content stored at a target client device of a plurality of target client devices; locating a content match responsive to the causing action, the content match corresponding to the requested content and having predefined authorization access information; determining whether predetermined authorization access information associated with a requesting client device comports with the predefined authorization access information; if not, denying access to the requested content to a user; and if so, providing access to the requested content to the user; wherein the action of providing comprises: transferring the requested content from a target client device of the plurality of target client devices to the requesting client device; and enabling the user to view the requested content via the requesting client device; wherein the action of determining comprises: comparing a plurality of rights holders from the predetermined authorization access information to a rights holder from the predefined authorization access information; and comparing subscription date information from the predetermined authorization access information to an original broadcast date of the requested content from the predefined authorization access information; and wherein the plurality of content indexes are at least co-located with a head end of a multimedia content distribution system; and wherein the locating action is performed by the head end.
 2. The method as recited in claim 1, wherein the user supplies the predetermined authorization access information to the requesting client device.
 3. The method as recited in claim 1, wherein the method is effectuated by the requesting client device.
 4. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct a client device to perform the method as recited in claim
 1. 5. A client device for authorization access controlled content exchange, the client device configured to perform actions comprising: causing a plurality of content indexes to be searched to locate a match to requested content, each content index of the plurality of content indexes corresponding to content stored at a target client device of a plurality of target client devices; locating a content match responsive to the causing action, the content match corresponding to the requested content and having predefined authorization access information; determining whether predetermined authorization access information associated with the client device comports with the predefined authorization access information; if not, denying access to the requested content to a user; and if so, providing access to the requested content to the user by transferring the requested content from the target client device corresponding to the content match; wherein the action of determining comprises comparing subscription date information from the predetermined authorization access information to an original broadcast date of the requested content from the predefined authorization access information.
 6. The client device as recited in claim 5, wherein the client device is further configured to perform an action comprising: receiving a search request input, the search request input directed to the requested content based on at least one of a name, an identification, a broadcast channel, a broadcast time, a broadcast date, or a description.
 7. The client device as recited in claim 5, wherein the client device comprises at least one of a set-top box (STB), a personal computer (PC), a personal digital assistant (PDA), a mobile telephone (MT), a tablet PC, or a pocket or hand-sized PC.
 8. A client arrangement that is capable of authorization access controlled content exchange, comprising: profile means for profiling subscription information that indicates access rights to content; index means for indexing content that is stored at the client arrangement; search means for searching content that is stored remotely at a plurality of other client arrangements by searching a plurality of other index means, each other index means of the plurality of other index means corresponding to a particular other client arrangement of the plurality of other client arrangements; and access means for providing access to content located by the search means if the profile means indicates that access rights to the content located by the search means exist with respect to the client arrangement, the access means for transferring the content located at one of the plurality of other client arrangements responsive to the search means; wherein the access means comprises comparison means for comparing subscription date information from the predetermined authorization access information from the profile means to an original broadcast date of the content.
 9. The client arrangement as recited in claim 8, wherein the client arrangement comprises client means for a television-based entertainment environment.
 10. The client arrangement as recited in claim 8, wherein the search means comprises at least one of agent means for searching the plurality of other index means as located at the plurality of other client arrangements or agent means for searching the plurality of other index means as located at a head end of a multimedia content distribution system.
 11. A method for controlling content exchange in a television-based entertainment environment, the method comprising actions of: performing a search for content that is stored on a target client device of a plurality of target client devices with reference to authorization access information; comparing subscription date information from the authorization access information to an original broadcast date of the content from predefined authorization access information; and enabling access to the content if predetermined authorization access information comports with the predefined authorization access information by transferring the content from the target client device to a requesting client device, the requesting client device requesting the search.
 12. The method as recited in claim 11, wherein the content comprises multimedia content.
 13. The method as recited in claim 11, wherein the authorization access information comprises at least one of a user profile, a parental rights setting, or data protecting broadcast rights across recorded media.
 14. The method as recited in claim 11, wherein the action of performing comprises: locating the content on the target client device; and determining whether the predetermined authorization access information comports with the predefined authorization access information.
 15. The method as recited in claim 11, wherein the action of performing comprises: locating the content on the target client device by orchestrating the search from the requesting client device; and determining whether the predetermined authorization access information comports with the predefined authorization access information.
 16. The method as recited in claim 11, wherein the action of performing comprises: locating the content on the target client device by orchestrating the search from a server device of the television-based entertainment environment; and determining whether the predetermined authorization access information comports with the predefined authorization access information.
 17. The method as recited in claim 11, wherein the action of performing comprises: locating the content on the target client device by orchestrating the search from a head end of the television-based entertainment network; and determining whether the predetermined authorization access information comports with the predefined authorization access information.
 18. The method as recited in claim 11, wherein the action of enabling further comprises: displaying a positive match result from the search; and providing an opportunity to request a transfer of the content to the requesting client device.
 19. The method as recited in claim 11, wherein the predetermined authorization access information is associated with a requesting user of the requesting client device, and the predefined authorization access information is associated with the content.
 20. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct an electronic apparatus to perform the method as recited in claim
 11. 21. A method for authorization access controlled content exchange, the method comprising actions of: receiving a search request for content from a requesting user; locating a search match for the content, the content stored by a different user at a client device; determining whether the requesting user has access rights to the content responsive to authorization access information; if not, denying access to the content to the requesting user; and if so, providing access to the content to the requesting user by transferring the content from the different user after the locating; wherein the action of determining comprises: comparing a profile that corresponds to the requesting user with rights holder information that corresponds to the content; and wherein the profile includes subscription date information associated with the requesting user and at least one television channel or television network to which the requesting user subscribes, and the rights information includes an original broadcast date of the content and at least one television channel or television network that provided the content, and wherein the comparing comprises comparing the subscription date information associated with the requesting user to the original broadcast date of the content.
 22. The method as recited in claim 21, further comprising: reporting results of the search request to the requesting user prior to the providing.
 23. The method as recited in claim 22, wherein the action of reporting comprises: presenting a content match to the requesting user, the requesting user comprising an operator of a client device; and providing the operator an opportunity to receive the content for storage at the client device from the different user.
 24. The method as recited in claim 21, wherein the requesting user comprises a client device; and wherein the actions of receiving, locating, and determining are effectuated by a search server of a multimedia content distribution system.
 25. The method as recited in claim 21, wherein the actions of receiving, locating, and determining are effectuated by a client device of a multimedia content distribution system.
 26. The method as recited in claim 21, wherein the action of locating comprises: searching a plurality of content indexes for the content, each content index of the plurality of content indexes indicating what content is stored on a respective client device of a plurality of client devices.
 27. The method as recited in claim 26, wherein each content index of the plurality of content indexes includes a plurality of content index entries, each content index entry of the plurality of content index entries including at least an identification of a content item that is stored on the respective client device of the plurality of client devices.
 28. The method as recited in claim 21, wherein the action of locating is effectuated by the requesting user and the different user.
 29. The method as recited in claim 21, wherein the action of locating is effectuated by a search server that has access to a plurality of content indexes, a content index of the plurality of content indexes corresponding to the different user and including a content index entry directed to the content.
 30. The method as recited in claim 21, wherein the authorization access information includes predetermined authorization access information that is associated with the requesting user and predefined authorization access information that is associated with the content; and wherein the action of determining comprises: comparing the predetermined authorization access information to the predefined authorization access information to determine whether the predetermined authorization access information comports with the predefined authorization access information.
 31. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct an electronic apparatus to perform the method as recited in claim
 21. 32. A method for authorization access controlled content exchange, the method comprising actions of: receiving a search request for content from a requesting user; determining whether special rights are needed to access the content; if special rights are needed to access the content, then determining whether the requesting user has access rights to the content responsive to authorization access information; if the requesting user does not have access rights to the content, then denying access to the content to the requesting user; if the requesting user does have access rights to the content, then performing a search to locate the content using a plurality of content indexes, the plurality of content indexes reflecting content stored at a plurality of client devices; reporting results of the search to the requesting user; and providing the requesting user an opportunity to elect to transfer the content from a particular client device of the plurality of client devices to a client device of the requesting user; wherein the action of determining whether the requesting user has access rights to the content comprises comparing subscription information from the authorization access information to an original broadcast date of the content.
 33. The method as recited in claim 32, wherein the action of determining whether special rights are needed to access the content comprises: consulting a database to search for predefined authorization access information that is associated with the content.
 34. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct an electronic apparatus to perform the method as recited in claim
 32. 35. A method for authorization access controlled content exchange, the method comprising actions of: receiving a search request for content from a requesting user; performing a search for the content responsive to the received search request by searching a plurality of content indexes, each content index of the plurality of content indexes reflecting content items stored at target client devices; determining whether a search match has been found from the search; if a search match has not been found, reporting a no match search result to the requesting user; if a search match has been found, determining whether the requesting user has rights to the content; if the requesting user has rights to the content, (i) reporting a match search result to the requesting user and (ii) scheduling a transfer of the content from a target client device of the plurality of target client devices to the requesting user; and if the requesting user does not have rights to the content, reporting a no access result to the requesting user; wherein the determining whether the requesting user has rights to the content comprises comparing subscription information associated with the requesting user with an original broadcast date of the content.
 36. The method as recited in claim 35, further comprising if the requesting user has rights to the content, (iii) recording the transfer at a head end of a television-based entertainment network.
 37. The method as recited in claim 35, wherein the action of reporting a no access result to the requesting user comprises: providing the requesting user an opportunity to subscribe to a service and thereby gain access to the content.
 38. The method as recited in claim 35, wherein the action of reporting a no access result to the requesting user comprises: providing the requesting user an opportunity to remit a fee to thereby gain access to the content.
 39. The method as recited in claim 35, wherein the action of determining whether the requesting user has rights to the content comprises: determining whether the requesting user had rights to the content when the content was distributed; and determining whether the requesting user currently has rights to the content.
 40. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct an electronic apparatus to perform the method as recited in claim
 35. 41. A method for authorization access controlled content exchange, the method comprising actions of: receiving a search request for desired content from a requesting user, the search request including at least one search parameter; searching a plurality of content indexes to match the at least one search parameter, each content index of the plurality of content indexes corresponding to content stored at a target client device of a plurality of target client devices; locating a content match responsive to the searching action, the content match corresponding to the desired content and having predefined authorization access information; determining whether predetermined authorization access information associated with the requesting user comports with the predefined authorization access information; if the predetermined authorization access information does not comport with the predefined authorization access information, denying access to the desired content to the requesting user; and if the predetermined authorization access information does comport with the predefined authorization access information, providing access to the desired content to the requesting user by transferring the desired content from a target client device that stores the desired content; wherein the determining whether predetermined authorization access information comports with the predefined authorization access information comprises comparing subscription information from the predetermined authorization access information to an original broadcast date of the desired content from the predefined authorization access information.
 42. The method as recited in claim 41, wherein the requesting user comprises at least one of a client device or a viewer of the client device.
 43. The method as recited in claim 41, wherein the method is effectuated by a head end of a multimedia content distribution system.
 44. The method as recited in claim 43, wherein the plurality of content indexes are at least co-located with the head end of the multimedia content distribution system.
 45. The method as recited in claim 43, wherein the plurality of content indexes are located at the plurality of target client devices.
 46. The method as recited in claim 41, wherein the predetermined authorization access information is received with the search request.
 47. The method as recited in claim 41, wherein the predetermined authorization access information is extracted from a profile of a plurality of profiles, the profile corresponding to the requesting user.
 48. The method as recited in claim 41, wherein the predefined authorization access information is extracted from the content index of the plurality of content indexes that provides the content match.
 49. The method as recited in claim 41, wherein the predefined authorization access information identifies a premium content provider and the predetermined authorization access information identifies a plurality of premium content providers; and wherein the predetermined authorization access information is determined to comport with the predefined authorization access information if the premium content provider is among the plurality of premium content providers.
 50. One or more electronically-accessible media comprising electronically-executable instructions that, when executed, direct an electronic apparatus to perform the method as recited in claim
 41. 51. A system for authorization access controlled content exchange, comprising: a database, the database including a plurality of profiles and a plurality of content indexes; each profile of the plurality of profiles including predetermined authorization access information for a corresponding client device of a plurality of client devices, and each content index of the plurality of content indexes including predefined authorization access information for content stored at the corresponding client device of the plurality of client devices; a search server, the search server capable of receiving a content search request for requested content from a requesting client device and performing a search responsive to the content search request using the plurality of content indexes; the search server adapted to provide access to the requested content if the requesting client device has access rights to the requested content and to deny access to the requested content if the requesting client device does not have access rights to the requested content; the search server also adapted to compare subscription date information from the predetermined authorization access information to an original broadcast date of the requested content from the predefined authorization access information; and a communications part, the communications part adapted to transfer the requested content from a particular client device of the plurality of client devices to the requesting client device if the search server is to provide access to the requested content because the requesting client device has access rights to the requested content.
 52. The system as recited in claim 51, wherein: the communications part is further adapted to facilitate communications between the system and the plurality of client devices to maintain consistency between the plurality of profiles and the plurality of content indexes and respective profiles and content indexes stored at the plurality of client devices.
 53. The system as recited in claim 51, wherein the database and the search server comprise at least a portion of a head end of a multimedia content distribution system.
 54. The system as recited in claim 51, wherein the search server comprises electronically-executable instructions.
 55. The system as recited in claim 51, wherein the search server is further adapted to determine whether the requesting client device has access rights to the requested content by determining whether the predetermined authorization access information from a profile that corresponds to the requesting client device comports with the predefined authorization access information from a content index that corresponds to the requested content.
 56. The system as recited in claim 51, wherein each profile of the plurality of profiles is linked to a content index of the plurality of content indexes according to the corresponding client device of the plurality of client devices. 